Method and system for tracking containers

ABSTRACT

A method for tracking containers. The method includes manufacturing containers, including forming the containers and serializing them with machine-readable codes. The method further includes using the machine-readable codes to store data associated with the containers, and supplying the containers to a customer. The method still further comprises receiving from the customer, data obtained from customer-readings of the machine-readable codes; and receiving from one or more other locations in a distribution chain in which the containers travel, data obtained from readings of the machine-readable codes at those locations. The method still further comprises comparing the data from the customer-readings and other readings of the machine-readable codes across product brands, product distribution channels, and/or container types, and providing the data to the customer. In at least some embodiments, the method further comprises receiving from the customer a compensation for the containers, for example, a per-refill compensation.

The present disclosure is directed to containers and, more particularly,to methods and systems for tracking and collecting data aboutcontainers.

BACKGROUND AND SUMMARY OF THE DISCLOSURE

Containers may be used to package and supply a variety of differentgoods including, but not limited to, beverages and other food productspackaged in glass or plastic containers, for example, bottles. Thesecontainers are designed and intended to travel through a fairlyextensive distribution or supply chain. Some containers are reusable inthat the container is intended to be reused numerous times, travelingrepeatedly through a distribution or supply chain. For instance, acontainer manufacturer may first supply a container to a customer (e.g.,bottler) who then packages its good(s)/product(s) in the container. Thecontainer may then be shipped to a point of sale, for example, a retailstore, a restaurant, etc., where a consumer or end user may purchase thegood. Subsequent to the consumption or use of the good(s) in thecontainer, the empty container may be returned to a return or collectionfacility, which may then return the container to either the manufactureror the initial customer (e.g., bottler). Reusable containers may becleaned and re-filled by a customer (e.g., bottler) or they may bereturned to the container manufacturer at such time that the reusablecontainer has reached the end of its useful life; the containermanufacturer may re-melt the container. Non-reusable containers may bereturned to the container manufacturer for re-melting. Unfortunately,data regarding how a particular container travels through thedistribution chain is either unavailable or limited, and as such, is oflittle use to the container manufacturer, the initial customer of thecontainer, or to other parties.

A general object of the present disclosure, in accordance with oneaspect of the disclosure, is to provide a method and system for trackingand collecting data about containers as the containers travel throughvarious points in a distribution chain using permanent and uniqueidentifiers for each container. Data collected at different points inthe distribution chain may be used by the container manufacturer asinput to strengthen or lighten the containers or otherwise improvecontainer manufacturing and/or design, or data may be provided (e.g.,sold) to the customer (e.g., bottler) to evaluate overall cost of thecontainer, number of times a container is refilled, the appearance anduseful life of a container, or other useful metrics or qualitativeinformation, or data may be provided to an interested party who may thenuse the data for a variety of purposes, for example, to evaluate how oneor more containers are being used and/or how they perform in the field,how the manufacturer is compensated for the container, and the like.

The present disclosure embodies a number of aspects that can beimplemented separately from, or in combination with, each other.

In accordance with one aspect of the disclosure, a method is providedthat includes manufacturing containers, including forming the containersand serializing them with machine-readable codes integral to andirremovable from the containers. The method further comprises using themachine-readable codes to store data associated with the containers,including at least one of a date of container manufacture, a time ofcontainer manufacture, production facility data, or container qualitydata. The method still further comprises supplying the containers to acustomer (e.g., bottler), and receiving, from the customer, dataobtained from customer-readings of the machine-readable codes andincluding data relating to the filling of the containers. The method yetstill further comprises receiving, from a seller of products includingthe containers, data obtained from seller-readings of themachine-readable codes and including at least one of a date of containersale, a time of container sale, or seller-specific data. The methodfurther comprises analyzing the data from the customer-readings andseller-readings to determine certain information relating to thecontainers.

In accordance with another aspect of the disclosure, there is provided amethod for container manufacturing and design. The method comprisesdesigning and manufacturing containers including forming the containersand serializing each with a unique machine-readable code integral to andirremovable from the containers; and using the machine-readable codes tostore data associated with the containers, including at least one of adate of container manufacture, a time of container manufacture,production facility data, or container quality data. The method furthercomprises supplying the containers to a customer; and receiving, fromthe customer, data obtained from readings of the machine-readable codesand including data relating to the filling of the containers. The methodfurther includes using the data received from the customer as feedbackfor modifying a design of the containers to, for example, strengthen orlighten the containers, or for other purposes, for example, to increasespeed and/or accuracy in filling, to track authentic products throughtheir end use, and/or to detect counterfeit products that have enteredthe marketplace.

In accordance with yet another aspect of the disclosure, there isprovided a system comprising: a central server; a database accessible bythe server and providing storage for data relating to containerstraveling within a distribution chain; and a plurality of electroniccode readers located at different points throughout the distributionchain, the code readers being configured to read unique machine-readablecodes carried by the containers and to electronically communicate dataobtained as a result of the readings of the machine-readable codes tothe central server, and wherein each machine-readable code isrepresentative of data associated with the corresponding container. Inan embodiment, the central server is configured to: receive from acustomer to whom one or more containers were supplied, data obtainedfrom customer-readings of the machine-readable codes of those containersby one or more of the plurality electronic code reader(s) located at thecustomer, wherein the data includes data relating to the filling of thecontainers; receive from a seller of products including the containers,data obtained from seller-readings of the machine-readable codes byanother one or more of the electronic code reader(s) located at theseller, wherein the data includes at least one of a date of containersale, a time of container sale, or seller-specific data; and generate areport based on the data from the customer readings and seller readings.

In accordance with yet still another aspect of the disclosure, there isprovided method comprising manufacturing containers, including formingthe containers and serializing the containers with machine-readablecodes integral to and irremovable from the containers, and using themachine-readable codes to store data associated with the containers,including at least one of a date of container manufacture, a time ofcontainer manufacture, production facility data, or container qualitydata. The method further comprises supplying the containers to acustomer, and receiving from the customer, data obtained fromcustomer-readings of the machine-readable codes and including datarelating to the filling of the containers. The method still furthercomprises earning revenue from the customer in accordance with anestablished pricing model, which, in at least some embodiments whereinthe containers are reusable containers, takes into account the quantityof refills of the reusable containers.

In accordance with a further aspect of the disclosure, there is provideda method comprising manufacturing containers, including forming thecontainers and serializing the containers with machine-readable codesintegral to and irremovable from the containers, and using themachine-readable codes to store data associated with the containers,including, at least one of a date of container manufacture, a time ofcontainer manufacture, production facility data, or container qualitydata. The method further comprises supplying the containers to acustomer, and receiving, from the customer, data obtained fromcustomer-readings of the machine-readable codes and including datarelating to the filling of the containers. The method still furthercomprises receiving, from one or more other locations in a distributionchain in which the containers travel, data obtained from readings of themachine-readable codes at those locations. The method yet still furthercomprises receiving compensation from the customer for the containers inaccordance with an established pricing model, and providing the data tothe customer in exchange for the compensation received from thecustomer.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure, together with additional objects, features, advantagesand aspects thereof, will be best understood from the followingdescription, the appended claims, and the accompanying drawings, inwhich:

FIG. 1 is a perspective view of an illustrative embodiment of anoperating environment comprising a system for tracking and collectingdata about container(s) as the container(s) travel within or through adistribution chain;

FIG. 2 is an elevation view of a container having a machine-readablecode applied thereto that may be tracked using the system illustrated inFIG. 1 ; and

FIGS. 3-5 are flowcharts showing various steps of illustrativeembodiments of a method for tracking and collecting data aboutcontainer(s) as the container(s) travel within or through a distributionchain.

DETAILED DESCRIPTION

FIG. 1 depicts an operating environment that comprises a system 10 thatmay be used to implement the method disclosed herein. The system 10generally includes a central server 12, a plurality of electronic codereaders 14 (e.g., code readers 14 a, 14 b, 14 c, etc.) configured toread machine-readable codes, and database or data repository 16 that ispart of or accessible by the server 12. It should be understood that thedisclosed method can be used with any number of different systems and isnot specifically limited to the operating environment shown in FIG. 1 .The following paragraphs provide a brief overview of one illustrativeembodiment of the system 10; however, other systems not shown here couldemploy the disclosed method as well.

The central server 12 may be used to control, govern, or otherwisecontrol and/or manage certain operations or functions of the system 10,including performing or facilitating some or all of the functionality ofthe method described below. The server 12 may be a standalone componentor part of either another component or a larger system or network.Further, the central server 12 may comprise a single server element or aplurality of server elements. In the latter instance, the individualserver elements may be electrically connected to each other to allowcommunication therebetween. The central server 12 may be implementedwith a combination of hardware, software, firmware, and/or middleware,and, in an illustrated embodiment, may include one or more electronicprocessors or processing devices 18 and one or more electronic memorydevices 20. In an embodiment, the memory device 20 may be a component ofthe processing device 18, while in another embodiment, it may beseparate and distinct therefrom but accessible thereby.

The processing device 18 may comprise any type of suitable electronicprocessor or processing device (e.g., programmable microprocessor,microcontroller, center processing unit (CPU), application specificintegrated circuit (ASIC), etc.) that is configured to receive andprocess data and/or execute appropriate programming instructions forsoftware, firmware, programs, algorithms, scripts, etc., to performvarious functions, for example and without limitation, those relating tothe method described below. The processing device 18 may further includean input/output (I/O) or communication interface(s) 22 through whichinput and output signals may pass, for example, those communicatedbetween the code readers 14 and the server 12 or between the server 12and other components that may or may not be part of the system 10. Thecommunication interface(s) 22 may include, or be electrically connectedto and configured for communication with, certaincommunication-supporting infrastructure (e.g., one or more knowncomponents/devices, for example, routers, modems, antennas, electricalports, transceivers, etc.), and is/are configured to communicate withvarious components of the system 10 via a public or private network orusing other suitable communication techniques or protocols including,but not limited to, one or more of those described below.

The memory device 20 may include, for example, random access memory(RAM), read only memory (ROM), hard disk(s), universe serial bus (USB)drive(s), memory card(s), or any type of suitable electronic memorymeans and may store a variety of data. This includes, for example,software (e.g., code or logic), firmware, programs, algorithms, scripts,and other electronic instructions that, for example, are required toperform one or more of the functions described herein; and, in anembodiment, various data structures (e.g., databases, for example,database 16) for storing various information and data, including thatrequired to perform some or all of the functions or method describedherein.

As will be described in greater detail bellow, the server 12 may beconfigured and operable to receive data from one or more othercomponents of the system 10 (e.g., code reader(s) 14), and to store thereceived data in one or more databases 16 stored in a suitableelectronic memory device, for example and without limitation, the memorydevice 20 of the central server 12. Additionally, in at least certainembodiments, the central server 12 may also be configured to process andcompile data that it receives and/or that is stored in the database 16,to generate reports relating to the received/stored data, to generateand/or interface with user interfaces displayed on a display deviceassociated with the server 12 and/or the code readers 14 to provide datato and/or receive data from a user of the system 10.

The code readers 14 of the system 10 may be used to readmachine-readable codes carried by containers, for example, the container24 shown in FIG. 2 having one or more unique machine-readable code(s) 26associated therewith, and, in at least some embodiments, to obtain thedata contained within or represented by the machine-readable code(s) 26.The code readers 14 may comprise or include any number of devices knownin the art, for example and without limitation, laser scanners, imagescanners, charge coupled device (CCD) scanners, and camera-basedreaders, to cite just a few possibilities. And the code readers 14 maycomprise handheld devices (e.g., handheld scanners, smart phones,tablets, or other personal digital electronic devices configured tocapture an image or to scan or read a machine-readable code, etc.),non-handheld devices, or a combination of both handheld and non-handhelddevices.

In any event, the code readers 14 may comprise any knownmachine-readable code readers known in the art, and may include acombination of hardware, software, and/or other components that enablesthe scanning or reading of machine-readable codes, among potentiallyother functionality.

For example, the code readers 14 may include means for acquiring animage of the code 26 and/or for detecting and decoding the code 26 beingscanned. As shown in FIG. 1 with respect to code reader 14 a, each ofthe code readers 14 may include an electronic processor or processingdevice 28 and an electronic memory device 30 that is part of oraccessible by the processing device 28.

Similar to the processing device 18 of the central server 12, theprocessing device 28 of the code reader 14 may include any type ofsuitable electronic processing device (e.g., programmablemicroprocessor, microcontroller, central processing unit (CPU),application specific integrated circuit (ASIC), etc.) that is configuredto process data and/or execute appropriate programming instructions forsoftware, firmware, programs, applications, algorithms, scripts, etc.,necessary to perform various functions of the code reader 14. The memorydevice 30 may include, for example, random access memory (RAM), readonly memory (ROM), hard disk(s), universe serial bus (USB) drive(s),memory card(s), or any type of suitable electronic memory means and maystore a variety of data. This includes, for example, software (e.g.,code or logic), firmware, programs, applications, algorithms, scripts,etc., required to perform functions of the code reader 14.

In at least certain embodiments, the code readers 14 may also includeone or more components to enable a user to manually provide or inputcertain data relating to the container(s) to which the machine-readablecode(s) being scanned or read by the code reader 14 correspond. Thisdata may include, for example, container location, container contents,container inspection data, date and/or time data, and other useful data.More particularly, the code reader 14 may include a user interface (notshown), for example and without limitation, a touch screen, keypad,keyboard, etc., that a user may utilize and/or manipulate to providedata relating to one or more containers. Each of the code readers 14 mayfurther include one or more communication interfaces 32 that may includeor be electrically connected to certain communication-supportinginfrastructure (e.g., one or more known components/devices, such as, forexample, routers, modems, antennas, electromechanical ports,transceivers, etc.) to allow for the communication and exchange of databetween the code reader 14 and one or more other components of thesystem 10, for example, the central server 12.

In some embodiments, rather than the code reader 14 being configured toenable or allow a user to provide data relating to container(s) beingscanned or read (e.g., via a user interface thereof), another componentof the system 10 may provide this functionality. For example, in anillustrative embodiment, one or more of the code readers 14 may beelectrically connected to, for example, a computer 34 or other likedevice having one or more user interfaces (e.g., touch screen, keypad,keyboard, mouse, etc.) that a user may utilize to provide data to thecentral server 12. In addition to the user interface(s), the computer 34or other like device may further include an electronic processor orprocessing device 36 and an electronic memory device 38 that isaccessible by the processing device 36. The processing device 36 issimilar to those described above in that it may include any type ofsuitable electronic processing device (e.g., programmablemicroprocessor, microcontroller, central processing unit (CPU),application specific integrated circuit (ASIC), etc.) that is configuredto process data and/or execute appropriate programming instructions forsoftware, firmware, programs, applications, algorithms, scripts, etc.necessary to perform various functions. Likewise, the memory device 38is similar to those described above in that it may include any type ofsuitable electronic memory means and may store a variety of data. Thisincludes, for example, software (e.g., code or logic), firmware,programs, applications, algorithms, scripts, etc., required to performvarious functions. The computer 34 may further include one or morecommunication interfaces 40 that may include or be electricallyconnected to certain communication-supporting infrastructure (e.g., oneor more known components/devices, such as, for example, routers, modems,antennas, electromechanical ports, transceivers, etc.) to allow for thecommunication and exchange of data between the computer 34 and a codereader 14, as well as between the computer 34 and the central server 12.Accordingly, in an embodiment wherein one or more of the code readers 14is connected to a computer 34, the communication interface 32 of thecode reader 14 may be electrically connected to a communicationinterface 40 of the computer 34, and another communication interface 40of the computer 34 may be electrically connected to the central server12 via a suitable communication network, for example, a private orpublic network (e.g., the internet) or using other suitablecommunication techniques or protocols including, but not limited to, oneor more of those described elsewhere herein. The computer 34 may receivedata from the code reader 14 following the scanning or reading of a codecarried by a container, package the scanned data with the user-provideddata via the computer 34, if applicable, and then communicate all of thedata to the central server 12.

While certain code readers and arrangements relating thereto have beendescribed above, it will be appreciated that the present disclosure isnot limited to the use of any particular type of code reader(s) orcorresponding arrangement(s). Additionally, the system 10 may includeand/or be configured to support any number of code readers 14. As willbe appreciated in view of the description of the method set forth below,code readers 14 may be distributed at different points or locationsthroughout a distribution chain in which containers travel (e.g.,container manufacturer, customer, point of sale, consumer/end user,return/collection center, etc.). Accordingly, the system 10 may includeone or a plurality of code readers, and thus, is not limited to anyparticular number of code readers 14.

As briefly described above, various components of the system 10 may beconfigured to communicate with each other to exchange data therebetween.This communication may be facilitated across a suitable communicationsnetwork through communication interfaces of the individual components.The communications network, identified as reference numeral 42 in FIG. 1, may comprise a wired or wireless network, for example, one or acombination of: a suitable Ethernet network; radio andtelecommunications/telephone networks (e.g., cellular networks, analogvoice networks, or digital fiber communications networks); or any othersuitable type of network and/or protocol (e.g., local area networks(LANs), wireless LANs (WLANs), broadband wireless access (BWA) networks,personal area networks (PANs), publicly switched telephone networks(PSTNs), etc.). The communications network 42 may be configured for usewith one or more standard communications technologies and protocols, andmay utilize links using known technologies, for example, Ethernet, IEEE802.11, integrated services digital network (ISDN), digital subscriberline (DSL), as well as other known communications technologies.Similarly, the networking protocols used on a network to which some orall of the components of the system 10 are interconnected may includemulti-protocol label switching (MPL), the user datagram protocol (UDP),the hypertext transport protocol (HTTP), the simple mail transferprotocol (SMTP), and the file transfer protocol (FTP), among othersuitable network protocols. In an embodiment, the transmission controlprotocol/Internet protocol (TCP/IP) may be used, in which case it willbe appreciated that each component configured for communication usingsuch a protocol can be configured with a static IP address or can be setup to automatically receive an assigned IP address from another deviceon the network. Further the data exchanged over such the network 42 maybe represented using technologies, languages, and/or formats, such asthe hypertext markup language HTML), the extensile markup language(XML), and the simple object access protocol (SOAP) among other suitabledata representation technologies. Accordingly, it will be appreciated inview of the foregoing that the communication between various componentsof the system 10 may be facilitated in any number of ways using anynumber of techniques, and therefore, the present disclosure is notlimited to any particular way or technique(s); rather any suitable wayor technique may be utilized.

The database 16 is configured to store data relating to containersmanufactured by a particular manufacturer. The data stored in thedatabase 16 may comprise, for example, data manually entered or input bythe manufacturer or by a user acting on the behalf of the manufacturer,including, for example, unique identifiers (e.g., serial numbers orcode) corresponding to each container manufactured by the manufacturer,data relating to where and when the containers were manufactured,container quality (i.e., inspection) data, etc., as well as datareceived at the central server 12 as a result of the scanning or readingof the machine-readable code(s) of one or more containers by one or morecode readers 14. Accordingly, and as shown in FIG. 1 , the database 16may be arranged or organized such that it contains a record for eachcontainer manufactured by the manufacturer, wherein the record containsdata relating to that particular container. Each record may, in turn, betied or associated to a particular customer to whom the correspondingcontainer was supplied to allow all of the data relating to a particularcustomer to be easily located and compiled. As data is received by thecentral server 12 from, for example, a code reader 14 or as result of ascan/read by a code reader 14, the processing device 18 of the server 12is configured to process the data to determine which container thereceived data corresponds to, and to then store the data in the recordin the database that is associated with that particular container. Thetype of data that may be stored in the database is essentially unlimitedand may include, for example and without limitation:manufacturer-related data (e.g., the date/time the container wasmanufactured, the production line used to manufacture the container, thedate/time the container was supplied to a customer, etc.);customer-related data (e.g., one or more of a date/time the containerwas filled by the customer, the contents of the container, a number oftimes the customer has filled/refilled the container, inspection datarelating to the container, a date(s) the container was supplied to adistributor or seller of products (or point of sale), the type ofpacking used to ship the containers (e.g., box packs), etc.);distributor-related data (e.g., one or more of a date/time the containerwas received by the distributor, a date/time the container was suppliedto a seller of products, the type of packing used to ship the containers(e.g., box packs), the name of the distribution center or channelshipped to, etc.); seller-related data (e.g., one or more of a date/timethe container was received by the seller of products, a date/time thegoods/container was sold to an end user, etc.); and end user-relateddata (e.g., one or more of a date/time a consumer/end user purchased thegoods/container, a date/time the end user consumed or used the contentsof the container, etc.), to cite only a few possibilities. The database16 may be stored in or on a suitable electronic memory device, forexample, the memory device 20 of the central server 12 or anothersuitable memory device of or accessible by the central server 12.Accordingly, the present disclosure is not intended to be limited to thedatabase 16 being stored in or on any particular memory device.

In any event, and as will be described in greater detail below, the datastored in the database 16 may be used for a variety of purposes. Forexample, it may be used to evaluate how a particular container is usedby a customer, how it moves through the distribution chain, how itperforms as it repeatedly travels through the distribution chain, etc.The stored data may be compiled or agglomerated in a number of ways tosuit the purpose of its use, and in it at least some instances, may besold to customers and/or other interested parties. For example, the datamay be compiled or agglomerated on a customer-by-customer basis suchthat a particular customer can see how it is using the containers it issupplied with and/or how the containers it is supplied with areperforming as they travel through the distribution chain (e.g., is thequality holding up). Using the agglomerated data, the customer may alsobe able to learn how different types of containers are used and/orperform, how the use and/or performance of the containers supplied to itby the manufacturer compare to the use and performance of containerssupplied to other customers, how the use and/or performance ofcontainers in different distribution chains compare to each other, etc.The data may also be used to determine compensation owed to (earned by)the manufacturer in an instance wherein a customer owes the manufacturera fee each time a container (e.g., reusable container) isfilled/refilled. Data may additionally or alternatively be used to trackauthentic products/containers through the distribution chain and enduse, or to identify counterfeit products/containers that have enteredthe distribution chain. Accordingly, it will be appreciated that thedata stored in the database 16 may be used for any number of purposes,including purposes not expressly described herein.

Turning now to FIG. 3 , an illustrative embodiment of a methodology thatmay be implemented or performed in part using, for example, theabove-described system 10 will be described. More particularly, FIG. 3illustrates a method of tracking and collecting data about containers asthe containers travel through a distribution or supply chain. It shouldbe noted that while certain steps of the methodology will be describedas being performed or carried out by one or more particular componentsof the system 10, in other embodiments, the steps may be performed bycomponents of the system 10 other than that or those described, orcomponents not part of the system 10 but configured for use therewith.Additionally, while the description of method 100 is with respect to thesystem 10, it will be appreciated that the implementation or applicationof method 100 is not limited to the particular composition orarrangement of the system 10 described above, but rather may beimplemented with or by any number of suitably configured or arrangedsystems.

In an illustrative embodiment, the method 100 includes a step 102 ofmanufacturing one or more, and in an embodiment, a plurality, ofcontainers. In at least some embodiments, some or all of the containersmanufactured in step 102 comprise reusable containers. In otherembodiments, however, some or all of the containers may comprisesingle-use or one-trip containers. Accordingly, the present disclosureis not intended to be limited to any particular type (e.g., reusable ornon-reusable) type(s) of containers. While the particular manner whichthe containers are manufactured is dependent on the type of container(e.g., glass, plastic, metal, etc.), any number of known manufacturingprocesses may be utilized. For example, a plastic container may bemanufactured using any number of plastic injection and/or blow moldingtechniques. Metal containers may be manufactured using, for example,metal stamping and drawing processes. Glass containers may bemanufactured using any number of glass manufacturing techniques, forexample and without limitation, those that include a “hot end” and a“cold end.” As is known in the art, the hot end may include one or moreglass melting furnaces to produce a glass melt, one or more formingmachines to form the glass melt into glass containers, and one or moreapplicators to apply a hot-end coating to the glass containers. The “hotend” also may include an annealing lehr, or at least a beginning portionof the annealing lehr, for annealing the glass containers therein.Through the lehr, the temperature may be brought down gradually to adownstream portion, cool end, or exit of the lehr. The “cold end” mayinclude an end portion of the annealing lehr, applicators to apply oneor more cold-end coatings to the glass containers downstream of theannealing lehr, inspection equipment to inspect the containers, andpackaging machines to package the containers.

In any event, in addition to forming of the containers, step 102 furtherincludes serializing the containers with machine-readable codes,including applying the codes to the appropriate containers. For purposesof this disclosure, the term “serializing” is intended to mean providingeach container with a unique identifier code. The machine-readable codesmay take any number of forms, including, but certainly not limited to,multi-dimensional data matrices, dot matrices, barcodes, and othersuitable machine-readable codes. Illustrative examples ofmachine-readable codes that may be suitable for the purposes describedherein are those described in U.S. Patent Publication Nos. 2013/0341228,2014/0116911, and 2015/0028110, the entire contents of which areincorporated herein by reference; though other codes may certainly beused. More particularly, the machine-readable codes may comprise anidentifying marker that includes or one more optically-readable elementsor combination of elements (e.g., dots, numbers, symbols, graphics, orother indicia) arranged in a particular manner. In an embodiment, themachine-readable codes applied to the containers may be integral to andirremovable form the containers. Integral and irremovable codes make itboth more difficult to produce and easier to identify counterfeitcontainers. The codes may be applied to the containers as part of thecontainer manufacturing process using any number of known techniques,for example and without limitation: laser etching the codes onto/intothe outer surface of the containers; stamping the codes onto/into theouter surface; utilizing embossing/debossing techniques; and/or via acombination of selective application of electromagnetic radiationfollowed by application of focused beam radiation or energy in a patterncorresponding to a desired code, to cite only a few possibilities.

Method 100 may further include a step 104 of using the machine-readablecodes to store data associated with the respective containers to whichthe codes correspond. As will be appreciated in view of the descriptionbelow, step 104 may comprise a substep of step 102, may be a separatestep performed after step 102, or may comprise a combination of both.

In some embodiments, step 104 comprises generating or defining themachine-readable codes to represent or identify certain data associatedwith the containers to which the codes correspond. For instance, themachine-readable codes themselves may identify manufacturing datarelating to the containers. For example, for a given container, the codeapplied thereto may identify at least one of the manufacturing plantused to produce the container, the production line used in themanufacture of the container, the date and/or time the container wasproduced, data relating to the quality of the container (i.e.,inspection data), and the like. To better illustrate, in oneillustrative example a machine-readable code may comprise or berepresentative of a six (6) digit number “######” wherein the firstdigit represents the manufacturing plant (e.g., “1 #####” for a firstplant, “2 #####” for a second plant, etc.), the second digit representsthe line at the plant that was used (e.g., “#1 ####” for a first line,“#2 ####” for a second line, etc.), the third and fourth digitsrepresent the month in which the container was manufactured (e.g., “##01##” for January, “##02 ##” for February, etc.), and the last two digitsrepresent the year in which the container was manufactured (e.g.,“####14” for 2014, “####15” for 2015, etc.). In certain instances, anadditional sequential or random character could be added to the code tocreate an identifier that is unique to the container to which itcorresponds. Accordingly, a code that comprises or represents the number“210614-ABCXYZ” identifies that the corresponding container wasmanufactured at “plant 2” using “line 1” in “June 2014,” and anidentifier of ABCXYZ that is unique to that container. It will beappreciated that the aforedescribed code was provided for illustrativepurposes only and that codes having more or less digits or taking otherforms (e.g., codes that alphabetic, alphanumeric, or containing othercharacters or indicia) may certainly be used instead. In any event, inan instance wherein the code comprises or represents such a characterstring, the code may comprise the string itself or a code that can bedecoded to obtain the string.

In another embodiment, rather than the machine-readable code itselfrepresenting certain data, step 104 may comprise generating or definingthe machine-readable codes so that they simply represent, for example,an identifier (e.g., an alphabetic, numeric, alphanumeric, etc.identification code) that is unique to the container to which it isapplied and that may be used to look-up data associated with thatidentifier that is stored, for example, in the database 16. In such anembodiment, data associated with the unique identifier, and thereforethe corresponding container (e.g., that data described above), may bemanually or automatically entered or loaded into the database 16.

In any event, each machine-readable code that is applied or carried by acontainer may be associated with a respective record stored in thedatabase 16. All data that is obtained by the central server 12 upon thescanning or reading of that code or otherwise (e.g., manually entereddata) may be associated with the appropriate container and then storedin the record within the database 16 that corresponds to that container.

In an embodiment, method 100 further includes a step 106 of supplyingthe containers to a customer, who, in an illustrative embodiment,comprises a bottler of food and/or beverage products. This may comprise,for example, loading a certain number of containers onto a truck, train,boat, airplane, or a combination thereof, and delivering them to thecustomer. Alternatively, the customer may pick up the containers at themanufacturer's facility. Regardless of how the containers are supplied,in an embodiment, the manufacturer may either manually enter certaindata into the records in the database 16 that correspond to thecontainer(s) being supplied, or may scan/read the machine-readable codeson the container(s) using a code reader 14 at the manufacturer'sfacility, which may then automatically add the data to the record withor without additional interaction on the part of the manufacturer (e.g.,the manufacturer may be prompted to identify/confirm that the datareceived from the code reader 14 is accurate). In either instance, thedata added to the record for a given container may comprise at least oneof a date and/or time the container was supplied to a customer, the nameof the customer, the geographic location of the customer and/ormanufacturer, and/or other useful data.

In an embodiment, step 106 may comprise supplying the containers to thecustomer at a market sale price (i.e., a price at which the containersare typically sold), while in another embodiment, and as will bedescribed below, the containers may be supplied at a price other than amarket sale price, for example, a reduced price that is below the marketsale price. Additionally, in at least certain embodiments, thecontainers being supplied may be contained within a pallet, and thecodes of the containers may be associated or correlated with anidentifier (e.g., code) corresponding to the pallet, and thatassociation or correlation may be stored, for example, in the database16.

Once the containers are received by the customer in step 106, method 100may include a number of steps that may be performed by the customer, oneor more of which may be optional. For example, and as illustrated inFIG. 4 , method 100 may include a step 108 of placing the suppliedcontainers into the customer's float inventory for later use, a step 110of washing the supplied containers using known washing techniques,and/or a step 112 of inspecting the supplied containers using knowninspection techniques. The inspection may be completed optically using acomparometer or a camera. The container may be inspected for thepresence of, for example, cracks, broken finishes, chips, bottle design,debris inside the container, and bottle integrity, to cite a fewpossibilities. Inspection may also be used to detect aesthetic issues,for example, external scuffing, scratches, and chips, to cite a fewpossibilities. The machine-readable codes on the containers may also bescanned or read in a step 114 using a machine-readable code reader 14 atthe customer's location, and information or data resulting fromthat/those scan(s)/reading(s) may be, for example and as will bedescribed in greater detail below, sent to the central server 12 andlogged in the database 16.

With continued reference to FIG. 4 , following step 106 and, ifapplicable, following one or more of steps 108-114 described above, themethod 100 may comprise a step 116 of filling the supplied containerswith a product. This may comprise manually filling the containers orautomatically filling the containers using an automated fill line at thecustomer's facility. Once the containers are filled in step 116, themachine-readable codes applied thereto may be scanned or read in a step118 using the machine-readable code reader 14 at the customer's locationand, as with step 114 described above, information or data resultingfrom that/those scan(s)/reading(s) may be, for example and as will bedescribed in greater detail below, sent to the central server 12 andlogged in the database 16. Whether or not the filled containers arescanned in step 118, method 100 may further include a step 120 ofinspecting the filled containers for, for example, fill height, properlabeling, and/or the presence of a cap, to cite a few possibilities.This inspection may be performed optically with a camera or may becompleted using one or more lasers or other type(s) of sensor(s). Method100 additionally or alternatively comprise a step 121 of storing thefilled containers in a suitable location until it is time to supply(e.g., ship) the containers to a distributor, a seller of products, orsome other recipient.

When it is time to supply the containers to, for example, a distributoror a seller of products, method 100 may include a step 122 ofscanning/reading the machine-readable code(s) of the containers, and/ora step 124 of shipping or otherwise conveying the containers to theintended recipient. In an instance wherein method 100 includes step 122,the codes of the containers may be scanned or read using themachine-readable code reader 14 at the customer's location andinformation or data resulting from that/those scan(s)/reading(s) may be,for example and as will be described in greater detail below, sent tothe central server 12 and logged in the database 16.

Upon receipt of the filled containers conveyed to the seller in step124, method 100 may include a step 126 of stocking or storing thecontainers at a sales location, which in an embodiment may comprise aretail store, a restaurant, a bar, or some other like establishment orsales location (e.g., vending machine, kiosk, etc.), from which thecontainers and product contained therein may be purchased by a consumeror end user. Each time a container/product is purchased by an end user,the seller of products may scan or read the machine-readable code of thecontainer in a step 128 using a machine-readable code reader 14 at theseller's location, and information or data resulting from that/thosescan(s)/reading(s) may be, for example and as will be described ingreater detail below, sent to the central server 12 and logged in thedatabase 16.

Following the sale of a container/product, the machine-readable code onthe container may be scanned/read by the end user one or more times in astep 130 using a machine-readable code reader 14 at the end user'slocation or accessible by the end user (e.g., a code reader in the formof, for example, a smart phone, tablet, PDA, handheld scanner, etc.).More particularly, the end user may scan the code when the container isopened, when the product is being consumed or used, and/or following theconsumption or use of the product. As with the readings or scansdescribed above, information or data resulting from the scan/reading instep 130 may be sent to the central server 12 and logged in the database16.

When the container is no longer needed by the end user, the end user mayreturn the (empty) container to a collection facility in a step 132. Atthe collection facility, the machine-readable code of the container maybe scanned or read in a step 134 using a code reader 14, and informationor data resulting from that/those scans may be sent to the centralserver 12 and logged in the database 16 in a step 134. The container maythen, in a step 136, be returned (e.g., picked up, shipped, or otherwiseconveyed or transferred) to, for example, the customer who originallyfilled the container, and in an instance wherein the container is areusable container, some or all of steps 108-136 may then be repeatedone or more times over the life of the container. It will be appreciatedin view of the foregoing that the method 100 provides a way in which acontainer may be tracked over its entire lifecycle from manufacture towhen the container is no longer used and is disposed of In other words,method 100 provides a way to track a container essentially from cradleto grave.

In addition to the steps described above, and as illustrated in, FIG. 3, method 100 may further include a step 138 of receiving the dataobtained or resulting from the reading(s) or scan(s) of themachine-readable codes of the containers in steps 114, 118, 122, 128,130, and/or 134. More particularly, and as described above, as thecontainers travel within a given supply or distribution chain, the codesof the supplied containers may be read or scanned by code readers 14located at one or more points in the distribution chain, including, butnot limited to, one or more of those distribution chain pointsidentified and described elsewhere herein. Data resulting from thosereadings or scans may then be packaged and communicated over a suitablecommunications network, such as network 42, to, for example, the centralserver 12 or another suitable component of the system 10 connected tonetwork 42, which then stores the data in the database 16.

By way of illustration, in at least some embodiments, step 138 (step 138a in FIG. 3 ) comprises receiving data obtained from thecustomer-readings of the machine-readable codes of one or morecontainers taken in one or more of steps 114, 118, and 122. For a givencontainer, this data may include, for example and without limitation,data relating to the customer, the filling of the container, and/or thesupplying of the container to another party. More particularly, in anillustrative embodiment, this data may include at least one of a date onwhich the container was filled, a time at which the container wasfilled, the contents of the container, a number of times the containerhas been used/filled (or reused/refilled) by the customer, an amount oftime that has elapsed since the container was last filled, a date and/ortime that the filled container was supplied to a distributor or sellerof products, the name and/or location of the recipient of the filledcontainer (e.g., distributor and/or seller of products), the name of thecustomer, the geographic location of the customer, the fill line thatthe customer used to fill the container, the batch number of the productthe container was filled with, data relating to the packing of thecontainer (e.g., type of packing used to ship the container (e.g., boxpacks)), or data relating to an inspection of the container performed bythe customer, to cite just a few possibilities.

In any event, the data received from the customer may comprise dataobtained as a result of the scanning or reading of the machine-readablecode on the container. For example, the code reader 14 at the customer'slocation may be programmed with or able to ascertain certain data (e.g.,some or all of that described above) that comprises or is automaticallyincluded as part of the data that is communicated to the central server12 when the code is scanned or read. Alternatively, the datacommunicated to the central server 12 in step 138 a may comprise dataobtained by a combination of the scanning or reading of the code anduser inputs. Regardless of the type of data that is received, thereceived data may be associated with the container to which itcorresponds and stored in the database 16 of the system 10 along withother information relating to that container, if applicable. Moreparticularly, in an embodiment, upon receiving data corresponding to aparticular container, the processing device 18 of the server 12 mayprocess the data to identify the container to which the received datacorresponds, access a record stored in the database 16 that isassociated with that container and that may contain data relating tothat container, and then store the received data in that record. Forexample, in an embodiment, the processing device 18 may process thereceived data to identify a unique identifier assigned to the containerto which the received data corresponds, access the record stored in thedatabase that is associated with that unique identifier, and then storethe received data in that record. While an illustrative way ofassociating the data received in step 138 with the container to which itcorresponds has been described above, it will be appreciated that thepresent disclosure is not limited to any particular way(s) of doing so;rather, any number of ways of arranging or organizing data may used inaddition to or instead of the particular way described above.

In addition to receiving data obtained from customer-readings of themachine-readable codes, step 138 (step 138 b in FIG. 3 ) may alsoinclude receiving data obtained from the seller-readings taken in step128 of machine-readable codes of one or more containers supplied to theseller by the customer. As described above, once the customer fills oneor more of the containers it was supplied with in step 106, the customermay supply that or those filled containers to a seller of products(e.g., a retail store, a restaurant, a bar, or other likeestablishment). As described above with respect to step 128, the sellerof products may scan or read the machine-readable codes of thosecontainer(s) one or more times (e.g., upon receipt of the containersfrom the customer, upon the stocking of the containers, upon sale to anend user, etc.). In response to that or those scan(s) or reading(s),data may be communicated to, for example, the server 12 of the system10. For a given container, this data may include, for example andwithout limitation, at least one of data relating to the seller (e.g.,geographic location, name, etc.), a date and/or time of receipt of thecontainer from the customer, a date and/or time of the sale of thecontainer/product to an end user, data relating to an inspection of thecontainer performed by the seller, or other useful information.

In any event, and as with the data received from the customer, the datareceived from the seller may comprise data obtained as a result of thescanning or reading of the machine-readable code on the container. Forexample, the code reader 14 at the seller's location may be programmedwith or able to ascertain certain data (e.g., some or all of thatdescribed above) that comprises or is automatically included as part ofthe data that is communicated to the central server 12 when the code isscanned or read. Alternatively, the data received in step 138 b maycomprise data obtained by a combination of the scanning or reading ofthe code and user inputs. Regardless of the type of data that isreceived from the seller readings, the received data may be associatedwith the container to which it corresponds and stored in the database 16of the system 10 along with other data relating to that container, ifapplicable. This may be done in a number of ways including, for exampleand without limitation, the way(s) described above with respect to datareceived as a result of customer readings of the codes, whichdescription will not be repeated but rather applies here with equalweight.

In at least some embodiments, step 138 (step 138 c in FIG. 3 ) mayadditionally or alternatively include receiving data obtained from theend user-readings of machine-readable codes of one or more containerssupplied to the end user by the seller of products taken in step 130. Asdescribed above, the seller may sell/distribute the product andcontainer received from the customer to an end user. The end user whoreceives the product may scan or read the machine-readable codes of thepurchased container one or more times using, for example, a code reader14 in the form of a smart phone, tablet, PDA, etc. (e.g., upon thepurchase of the container/product, the consumption or use of theproduct, etc.). In response to that or those scan(s) or reading(s), datamay be communicated to, for example, the server 12 of the system 10. Fora given container, this data may include, for example and withoutlimitation, at least one of data relating to the date and/or time of thescanning or reading of the code, a date and/or time of the purchaseand/or receipt of the product/container, the geographic location of thepurchase, the end user's geographic location, the end user's contactinformation (e.g., email address, telephone number, mailing address,etc.), a date and/or time of the consumption or use of the productcontained with the container, or other useful information.

In any event, and as with the data received from the customer and sellerof products, the data received from the end user may comprise dataobtained as a result of the scanning or reading of the machine-readablecode on the container. For example, the code reader 14 used by the enduser may be programmed with or able to ascertain certain data (e.g.,some or all of that described above) that comprises or is automaticallyincluded as part of the data that is communicated to the central server12 when the code is scanned or read. Alternatively, the data received instep 138 c may comprise data obtained by a combination of the scanningor reading of the code and user inputs. Regardless of the type of datathat is received from the end user readings, the received data may beassociated with the container to which it corresponds and stored in thedatabase 16 of the system 10 along with other data relating to thatcontainer, if applicable. This may be done in a number of waysincluding, for example and without limitation, the way(s) describedabove with respect to data received as a result of customer readings ofthe codes, which description will not be repeated but rather applieshere with equal weight.

In addition to the above, step 138 (step 138 d in FIG. 3 ) may furtherinclude receiving data obtained from the collection facility readings ofmachine-readable codes taken in step 134 of one or more containersreturned by or collected from end users. As described above with respectto steps 132 and 134, when a container purchased by an end user is nolonger needed, the end user returns the empty container to a collectionfacility. The collection facility may scan or read the machine-readablecodes of that container taken in step 134, and may then in step 136return the container to the customer to whom it was originally suppliedin step 106. In response to that scan or reading, data may becommunicated to, for example, the server 12 of the system 10. For agiven container, this data may include, for example and withoutlimitation, at least one of data relating to the collection facility(e.g., geographic location, name, etc.), a date and/or time of receiptof the container from the end user, a date and/or time of the return ofthe container to the customer, or other useful information.

In any event, the data received from the collection facility maycomprise data obtained as a result of the scanning or reading of themachine-readable code on the container. For example, the code reader 14at the collection facility may be programmed with or able to ascertaincertain data (e.g., some or all of that described above) that comprisesor is automatically included as part of the data that is communicated tothe central server 12 when the code is scanned or read. Alternatively,the data received in step 138 d may comprise data obtained by acombination of the scanning or reading of the code and user inputs.Regardless of the type of data that is received from the collectionfacility readings, the received data may be associated with thecontainer to which it corresponds and stored in the database 16 of thesystem 10 along with other data relating to that container, ifapplicable. This may be done in a number of ways including, for exampleand without limitation, the way(s) described above with respect to datareceived as a result of customer readings of the codes, whichdescription will not be repeated but rather applies here with equalweight.

It will be appreciated that while several examples have been provided ofpossible points or locations within a container supply or distributionchain at which a machine-readable code of a container may be read orscanned, and therefore, data relating to the corresponding containerobtained, the machine-readable codes of containers may certainly bescanned or read at points or locations in a distribution chain otherthan those described above, for example, at one or more intermediate orintervening locations or points to one or more of those described above(e.g., at a distributor or wholesaler that is between the customer andthe seller of products, among potentially others). Thus, it will beappreciated that the present disclosure is not intended to be limited toany particular locations or points within a supply chain at which amachine-readable code may be scanned or read and data obtained.

The data obtained in step 138 may be used in any number of ways. Forexample, in at least some embodiments, the method 100 may include a step140 of agglomerating or compiling the received data (as well as, in atleast certain embodiments, other stored data) in a particular way sothat it may be evaluated by, for example, the manufacturer, the customerto whom the containers were supplied in step 106, and/or otherinterested parties. Accordingly, in at least some embodiments, themethod 100 may comprise further a step 142 of providing, and in certaininstances, selling, the data to the customer and/or other interestedparties (e.g., other customers of the manufacturer in a particularindustry). In an embodiment, either step 140 or step 142 may includegenerating a report (e.g., electronic, hardcopy, or both) representativeof the agglomerated data that may then be provided to the customer instep 142.

The data may be compiled, agglomerated, and/or organized in step 140 inany number of ways including, but not limited to, one or more of theways described below. In an illustrative embodiment, step 140 comprisesperforming statistical or other analysis on the data, for example,comparing information relating to one container supplied to a customerwith information relating to another container supplied to the samecustomer to show how the different containers have travelled through thesupply chain. In another embodiment, step 140 may comprise comparingdata relating to one type of container with data relating to anothertype of container to show how the respective container types are usedand perform relative to each other. Step 140 may also or alternativelycomprise comparing data relating to containers of one product brand withdata relating to containers of one or more other product brands (e.g.,product brands of the same customer or product brands of differentcustomers) to show how containers used in different brands performand/or are used. Step 140 may also or alternatively include comparingdata for containers traveling in one distribution channel with data forcontainers traveling in a different distribution channel to show howcontainers are used or perform in different distribution channels. Step140 may additionally or alternatively comprise using the data to providea more complete snap-shot of a given industry or segment of an industry(e.g., beer, wine, spirits, etc.) from filling through actualconsumption, as opposed to through a point of sale (e.g., from check outscan at a retail establishment). Step 140 may additionally oralternatively comprise analyzing the received data (e.g., data receivedfrom customer-readings and seller-readings of the machine-readablecode(s) of one or more containers) to determine certain informationrelating to one or more of the supplied containers (e.g., one or more oflength of time a container was in the seller's inventory prior to sale,seller demographics, type of seller, etc.).

Accordingly, it will be appreciated in view of the foregoing that datacorresponding to containers supplied by the manufacturer to one or morecustomers may be agglomerated and used in any number of ways, including,but certainly not limited to, those described above. In any event, in anembodiment, the central server 12, and the processing device 18 thereof,in particular, is configured to perform step 140. It will beappreciated, however, that in other embodiments, step 140 may beperformed by a different component of the system 10, and thus, thepresent disclosure is not intended to be limited to step 140 beingperformed by any particular component of the system 10.

A party to whom the agglomerated data is provided in step 142 may usethe information or data in any number of ways and for any number ofpurposes. For example, in an instance wherein the data is provided tothe customer to whom the containers were initially supplied in step 106,the customer may be able to evaluate how it is using the containers itis supplied with. More particularly, the customer may be able todetermine how long a container remains in its float inventory, how muchtime elapses between refills or reuses of the containers, how long ittakes for a container supplied to a seller of products to ultimately bereturned to the customer, and how the quality of the containers isaffected as the containers travel (repeatedly) through at least certainpoints in the distribution chain based on inspection information that isreceived, to cite a few possibilities. The customer may also be able tolearn how other types of containers are used or perform, as well as howcontainers supplied by the manufacturer to other customers are usedand/or perform.

The knowledge gleaned from the data may then be used by the customer todetermine, for example, whether or not to alter the way it doesbusiness. More specifically, the data may allow the customer to betterunderstand its float inventory and may lead to more efficient use of thecontainers it is supplied with. The data may provide the customer a viewof the total float inventory, e.g., whether it is growing or shrinking,and to determine whether the containers in the float inventory aremoving quickly or slowly in one or more areas of the market. In responseto the data, the customer may, for example, decide to order more orfewer containers from the manufacturer; change the type of container(s)it uses; manage its float inventory and use the containers in itsinventory in a more efficient manner; incentivize the prompt return ofcontainers after an end user has used or consumed the contents of thecontainers using targeted advertising (e.g., television advertisementsencouraging the return of containers) and incentives (e.g., monetary orfinancial incentives payable upon the return of containers), especiallyin areas of the market where the float is particularly slow moving, andthe like. Additionally or alternatively, the customer may be able toevaluate how the product packaged in the containers is being consumed.For example, the customer may be able to determine whether the productremains on the shelf at a point of sale (e.g., seller of products) foran extended period of time, or is being sold quickly. The customer maybe able to determine who is consuming its product, and to then directmarketing or advertising to that specific end user. In such an instance,the method may include identifying an advertisement, offer, or othermarketing message to send to a given end user, and thencommunicating—electronically or otherwise—that advertisement or offer tothe end user. Similarly, the customer may be able to determine theactual moment of consumption on an individualized basis, and to thendirect a marketing message to that specific end user at, or shortlyafter, the moment of consumption. In an embodiment, a label on thecontainer may direct the end user to scan or “check-in” using thecontainer. Once scanned, the end user may be prompted to login or otheridentifying methods may be used to determine the demographics oridentity of the end user. In an embodiment, this data traffic may beinitially handled by the manufacturer, but could easily be transferredto the customer for handling. Otherwise, the manufacturer (e.g., a datacenter) could send marketing interactions to the end user's device. Thecustomer can then be charged for the interaction or for handling themarketing message and getting the consumption information.

Accordingly, it will be appreciated in view of the foregoing that thecustomer may use information it is provided within step 142 in anynumber of ways, including ways not expressly described herein. It willtherefore be further appreciated that the present disclosure is notintended to be limited to any particular use(s) of the providedinformation.

In addition to the customer using the data provided in step 142, in atleast certain instances, the data may also be useful to the containermanufacturer. For example, the manufacturer may use the information ordata received from different points in the distribution chain to learnhow a particular container design performs as containers of that designtravel through one or more distribution chains. The manufacturer mayalso use the data as feedback for modifying the design of a container.More particularly, the manufacturer may use the information to, forexample, strengthen, lighten, or otherwise enhance or optimize containermanufacture and/or design. Design improvements and weight changes may beintroduced into the float and overall reuse performance can be monitoredto determine which changes provide longer life or similar life withreduced weight. This information can be used to optimize the design ofthe float container over time. The information may also be used tomodify the container design for other purposes, for example, to increasespeed or accuracy in filling or to track authentic products/containersthrough their end use or to detect counterfeit products that haveentered the distribution chain. The manufacturer may also use at leastsome of the data received in step 138 for purposes of charging customersfor the containers it supplies, and more particularly, for implementingalternative pricing models for the containers. More specifically, in aninstance wherein a manufacturer wants to craft a creative and/orunconventional way in which to charge customers for containers (i.e.,other than charging a one-time sale price when the containers areordered or initially supplied), the manufacturer may use at least someof the information received from a customer for purposes of determiningrevenue or compensation earned by and owed to the manufacturer for thecustomer's use of the containers. Accordingly, in an embodiment, themethod 100 may include one or more steps in addition to or instead ofone or more of the previously-described steps that may be used forpurposes of monetizing the containers supplied to a customer by themanufacturer.

For example, and with reference to the illustrative embodiment shown inFIG. 5 , in an instance wherein the containers supplied to the customerin step 106 are reusable containers, the method 100 may include a step144 of establishing a sale price for containers that are comparable tothe reusable containers being supplied in step 106, the established saleprice being less than a market (one-time) sale price typically chargedfor the reusable containers. In an embodiment, step 144 comprisesestablishing a market sale price for comparable containers that are in anon-reusable form, which are typically less expensive than the marketsale price for reusable containers (e.g., by one-half or more, in someinstances). Following step 144, method 100 may further include a step146 of monetizing the reusable containers being supplied in relation tothe established market sale price for the non-reusable containers, anddoing so in an unconventional manner. Step 146 may take a number offorms including, but certainly not limited to, those described below.

In an illustrative embodiment, step 146 comprises establishing aninitial fee for the reusable container(s) that is less than orapproximately equal to the market sale price established in step 144 fornon-reusable containers, and therefore, less than the market sale pricefor reusable container(s). Step 146 further includes establishing aper-fill transaction fee to be charged each time the customer refillsthe supplied container(s). Accordingly, using information received instep 138 from customer-readings of machine-readable codes of containerssupplied to the customer in step 106, it can be determined when and/oror how many times the container(s) supplied to the customer have beenfilled/refilled, and then the manufacturer may then (periodically)charge the customer accordingly (e.g., each time a container isrefilled, after a certain number of refills of the container, after acertain total number of refills of a plurality of containers, etc.).Thus, in an embodiment, step 146 comprises selling the reusablecontainers supplied in step 106 to the customer at an initial price thatis below the market sale price established in step 144 and thereafterreceiving a per-fill compensation from the customer every time thecontainer(s) is/are refilled by the customer, wherein a sum of thereduced sale price plus a totality of the per-refill compensation may beequal to or greater than the market sale price established in step 144.

By way of example, assume, for purposes of illustration only, thefollowing: the market sale price of a reusable container is $0.40; themarket sale price of a comparable, “half-price” non-reusable containerestablished in step 144 is $0.20; the initial fee for a reusablecontainer established in step 146 is $0.20; the per-fill transaction feeestablished in step 146 is $0.015; and the container is refilled a totalof 20 times. Based on this scenario, the total revenue the manufacturerwill earn and receive from the customer is $0.50 (i.e., $0.20 (initialfee)+(20*$0.015) (per-fill fee)=$0.50), which is $0.10 more than the$0.40 market sale price of the reusable container.

In another illustrative embodiment, instead of establishing an initialfee for the reusable container(s) in step 146, step 146 includesestablishing only a per-fill transaction fee to be charged to thecustomer each time one of the supplied containers is refilled. This feemay be the same as the per-fill transaction fee established in thepricing model described above or may be different. In any event, usinginformation received in step 138 from customer-readings ofmachine-readable codes of container(s) supplied to the customer in step106, it can be determined when and/or or how many times the container(s)supplied to the customer have been refilled, and then the manufacturemay (periodically) charge the customer accordingly (e.g., the customermay be charged each time a container is refilled, after a certain numberof refills of the container, after a certain total number of refills ofa plurality of containers, etc.). Thus, in an embodiment, step 146comprises not selling the containers supplied in step 106 to thecustomer, but instead receiving a per-fill/refill compensation from thecustomer every time the container(s) is/are refilled by the customer,wherein a sum of the totality of the per-fill/refill compensation may beequal to or greater than the market sale price established in step 144.

By way of example, assume for purposes of illustration only that themarket sale price of a reusable container is $0.40 and the per-filltransaction fee established in step 146 is $0.03. If a container isrefilled 20 times, the total revenue the manufacturer will earn andreceive from the customer is $0.60 (i.e., (20*$0.03) (per fillfee)=$0.60), which is $0.20 more than the $0.40 market sale price of thereusable container.

In yet another illustrative embodiment, step 146 comprises establishinga one-time initial fee for the reusable containers that may be morethan, less than, or equal to the market sale price established in step144, and guaranteeing that the containers will withstand at least apredetermined minimum number of refills or reuses. Step 146 may furtherinclude establishing a per-fill transaction fee to be charged to thecustomer for every refill or reuse of a container in excess of thepredetermined minimum number of refills or reuses, and determining apro-rated portion of the initial fee to be returned to the customer ifthe guaranteed minimum number of refills or reuses is not met. In atleast some embodiments, the pro-rated portion that is returned is suchthat the manufacturer nonetheless receives at least the market saleprice determined in step 144, if not more. Accordingly, in anembodiment, step 146 comprises selling the containers supplied to thecustomer in step 106 at a price that is above, below, or equal to themarket sale price established in step 144, and guaranteeing to thecustomer a minimum quantity of reuses of the container, wherein if theguaranteed minimum quantity is exceeded, the manufacturer earns andreceives a per-refill compensation from the bottler every time thatcontainer is refilled by the customer in excess of the guaranteedminimum quantity, but wherein if the guaranteed minimum quantity is notmet, the manufacturer returns to the customer a pro-rated portion of theinitial sale price.

In certain instances, a customer could also be compensated whencontainers purchased by that customer are filled by another customer, orfor filling containers originally purchased or supplied to anothercustomer. For example, containers purchased by multiple customers in agiven geographic region may get mixed up as the containers are used,returned, and reused. Since the containers are uniquely identified, in aper-fill transaction wherein a customer fills a container that anothercustomer originally purchased, the per-fill transaction fee may bedirected to the customer actually filling the container, and/or the feecould be directed to the customer who originally purchased the containerand the customer filling the container may be debited for thetransaction fee or at least a pro-rata portion thereof.

In any event, and generally speaking, when the totality of the feesreceived by the manufacturer in any of the above-described pricingmodels are tabulated, the total revenue the manufacturer earns andultimately receives from a customer over the life of a container may beat least equal to each of the market sale price of the reusablecontainer and the market sale price of a non-reusable containerestablished in step 144, and therefore, the manufacturer ultimately mayearn more revenue for each reusable container.

It will be appreciated that while certain pricing models for monetizingcontainers are described in detail above, the present disclosure is notintended to be limited to the use of any particular model(s); rather,any suitable model may be used instead.

It will be further appreciated in view of the foregoing that in additionto providing benefits to the manufacturer (e.g., revenue streamthroughout the life of a container, potential for receiving more moneyfor a container than would otherwise be received using conventionalapproaches, etc.), alternative pricing models such as those describedabove may also benefit the customers, and therefore, may be anattractive option. More particularly, when a container is purchased forone-time sale price in the usual manner (i.e., when the container isordered or supplied to the customer), the expense is a capital expense.When purchased using an alternative pricing model like those describedabove, the expense may no longer be a capital expense but is now anoperating or a “cost of goods sold” expense, or the capital expense maybe substantially reduced. This frees up capital that can be used by thecustomer for other purposes. In at least some circumstances, thecustomer may be permitted to select the way in which they pay for thecontainers in order to try to maximize their expenditure. Accordingly,the customer may be permitted to choose to expense the sale of thecontainers on the first fill of the container (a one-time expense), orcan choose to capitalize the expense over the life of the container(per-fill arrangement). Additionally, in certain embodiments of method100, the customer may be provided with the agglomerated data (step 142)only in exchange for partaking in an alternative pricing model, whichprovides an additional incentive and benefit to the customer.Accordingly, the agglomerated data may be provided to the customer instep 142 in exchange for compensation earned by the manufacturer and, inat least certain instances, received from the customer, in accordancewith an established pricing model that may include a per-fill orper-refill compensation.

There thus has been disclosed a system for tracking containers thatfully satisfy one or more of the objects and aims previously set forth.The disclosure has been presented in conjunction with severalillustrative embodiments, and additional modifications and variationshave been discussed. Other modifications and variations readily willsuggest themselves to persons of ordinary skill in the art in view ofthe foregoing discussion. For example, the subject matter of each of theembodiments is hereby incorporated by reference into each of the otherembodiments, for expedience. The disclosure is intended to embrace allsuch modifications and variations as fall within the spirit and broadscope of the appended claims.

The invention claimed is:
 1. A method comprising the steps of:manufacturing containers, including forming the containers andserializing each of the containers with unique machine-readable codesthat are integral to and irremovable from the containers to produceserialized containers; using the machine-readable codes to store dataassociated with the serialized containers, including at least one of adate of container manufacture, a time of container manufacture,production facility data, or container quality data; supplying theserialized containers to a customer; receiving by a server and from thecustomer, data obtained from customer-readings of the machine-readablecodes by one or more electronic code readers, the data including aquantity of refills of the serialized containers; earning revenue fromthe customer dependent on a pricing model that is determined using thedata obtained from customer-readings of the machine-readable codes andthat is based at least in part on the quantity of refills of theserialized containers.
 2. The method of claim 1, wherein the serializedcontainers comprise serialized reusable containers, and the methodfurther comprises: establishing a market sale price for comparablecontainers in a non-reusable form otherwise identical to the serializedreusable containers; and monetizing the serialized reusable containersin relation to the established market sale price.
 3. The method of claim2, wherein the monetizing step includes selling the serialized reusablecontainers at an initial sale price that is below the established marketsale price, and receiving a per-refill compensation from the customerevery time a serialized reusable container is refilled by the customerwherein a sum of the initial sale price plus a totality of theper-refill compensation is greater than the established market saleprice.
 4. The method of claim 2, wherein the monetizing step includesnot selling the serialized reusable containers to the customer and,instead, receiving a per-refill compensation from the customer everytime a serialized reusable container is refilled by the customer whereina sum of the totality of the per-refill compensation is greater than theestablished market sale price.
 5. The method of claim 2, wherein themonetizing step includes selling the serialized reusable containers atan increased sale price that is above the established market sale price,and guaranteeing to the customer a minimum quantity of reuses of theserialized reusable containers, wherein if the guaranteed minimumquantity is exceeded, a manufacturer of the serialized reusablecontainers receives a per-refill compensation from the customer everytime a serialized reusable container is refilled by the customer inexcess of the guaranteed minimum quantity, but wherein if the guaranteedminimum quantity is not met, then the manufacturer returns a pro-ratedportion of the increased sale price to the customer.
 6. The method ofclaim 1, further comprising: associating the data from thecustomer-readings with the particular container(s) to which the datacorresponds; and storing the data in an electronic memory device withother data corresponding to the same container(s).
 7. The method ofclaim 1, wherein the data from the customer-readings is received from anelectronic scanning device configured to read the machine-readable codesof the containers.
 8. The method of claim 1, wherein the data from thecustomer-readings is received at an electronic processing device that isconfigured to receive the data.
 9. A method comprising the steps of:manufacturing containers, including forming the containers andserializing the containers with machine-readable codes that are integralto and irremovable from the containers to produce serialized containers;using the machine-readable codes to store data associated with theserialized containers, including, date of container manufacture, time ofcontainer manufacture, production facility data, container quality data,or a combination thereof; supplying the serialized containers to acustomer; receiving by a server and from the customer, data obtainedfrom customer-readings of the machine-readable codes by one or moreelectronic code readers, the data including data relating to the fillingof the serialized containers by the customer; receiving by the serverand from one or more other locations in a distribution chain in whichthe serialized containers travel, data obtained from readings of themachine-readable codes at those locations by one or more otherelectronic code readers; comparing the data from the customer-readingsand other readings of the machine-readable codes across at least one ofproduct brands, product distribution channels, or container types;receiving from the customer, compensation for the serialized containersin accordance with an established pricing model; and providingagglomerated data to the customer in exchange for the compensationreceived from the customer, wherein the agglomerated data includes or isderived from both the data obtained from customer-readings of themachine-readable codes and the data obtained from other readings of themachine-readable codes.
 10. The method of claim 9, further comprising:associating the data from the customer-readings with the particularcontainer(s) to which the data corresponds; and storing the data in anelectronic memory device with other data corresponding to the samecontainer(s).
 11. The method of claim 9, wherein the data from thecustomer-readings is received from an electronic scanning deviceconfigured to read the machine-readable codes of the serializedcontainers.
 12. The method of claim 9, wherein the data from thecustomer-readings is received at an electronic processing device that isconfigured to receive the data.
 13. The method of claim 9, wherein thestep of receiving from one or more other locations in a distributionchain in which the containers travel, data obtained from readings of themachine-readable codes at those locations comprises at least one of:receiving from a seller of products including the serialized containers,data obtained from seller-readings of the machine-readable codes andincluding at least one of a date of container sale, a time of containersale, or seller-specific data; or receiving from an end user of theproducts including the serialized containers, data obtained from enduser-readings of the machine-readable codes and including dates of theend user-readings, times of the end user-readings, or both.
 14. Themethod of claim 9, wherein receiving compensation from the customercomprises receiving a per-refill compensation every time a serializedcontainer is refilled by the customer.
 15. The method of claim 9,wherein a manufacturer of the serialized containers receives thecompensation according to the receiving step.
 16. The method of claim 1,wherein a manufacturer of the serialized containers earns the revenueaccording to the earning step.